Skip to content

[PULP-817] Django5 support and adjustments to make imp/exp work with django-imp-exp 4.x. #7288

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
gerrod3 wants to merge 1 commit into
base: 3.85
Choose a base branch
from
Open

[PULP-817] Django5 support and adjustments to make imp/exp work with django-imp-exp 4.x. #7288

gerrod3 wants to merge 1 commit into from
+28 −11

Conversation

@gerrod3
Copy link
Contributor

@gerrod3 gerrod3 commented Feb 6, 2026

(cherry picked from commit 793c0ad)

closes #5324.
closes #6988.

📜 Checklist

  • Commits are cleanly separated with meaningful messages (simple features and bug fixes should be squashed to one commit)
  • A changelog entry or entries has been added for any significant changes
  • Follows the Pulp policy on AI Usage
  • (For new features) - User documentation and test coverage has been added

See: Pull Request Walkthrough

@gerrod3 gerrod3 force-pushed the backport-6973-3.85 branch from 2e22647 to ac6b52d Compare February 6, 2026 19:30
@gerrod3 @cursoragent
[PULP-817] Django5 support and adjustments to make imp/exp work with …
c5a6340 
…django-imp-exp 4.x.

(cherry picked from commit 793c0ad)

closes pulp#5324.
closes pulp#6988.

Co-authored-by: Grant Gainey <ggainey@redhat.com>
Assisted by: cursor agent

Co-authored-by: Cursor <cursoragent@cursor.com>
@gerrod3 gerrod3 force-pushed the backport-6973-3.85 branch from ac6b52d to c5a6340 Compare February 6, 2026 20:12
dralley
dralley requested changes Feb 8, 2026
View reviewed changes
Copy link
Contributor

@dralley dralley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs a changelog to note that this is a breaking change w/r/t exports created before and after the Django Import/Export upgrade (if it is upgraded)

@dralley
Copy link
Contributor

dralley commented Feb 9, 2026

Also we need to document somehow that the Postgresql requirement changes for Django 5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@dralley dralley dralley requested changes

Requested changes must be addressed to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@gerrod3 @dralley